System and methods for zero-step customer proximity detection using mobile device low emissions beacons

ABSTRACT

A system and methods for zero-step customer proximity detection using mobile device low emissions beacons, which uses a customer mobile device, a single or plurality of BLUETOOTH™ low-emissions (BTLE) beacons, a network, a server, and an application that may operate separately on a mobile device and the single or plurality of BLUETOOTH™ low-emissions (BTLE) beacons, which allows businesses to detect known customers that come within a specified proximity of any connected BTLE beacons, and provide interactions with them on a zero-step and socially distanced basis, track their proximity to other customers and staff using similar applications, manage table assignments, offer deals or provide incentives to enter or patronize a business establishment.

CROSS-REFERENCE TO RELATED APPLICATIONS

application Ser. No. Date Filed Title Current Herewith A SYSTEM ANDMETHODS application FOR ZERO- STEP CUSTOMER PROXIMITY DETECTION USINGMOBILE DEVICE LOW EMISSIONS BEACONS Claims benefit of, and priority to:63/070,895 Aug. 27, 2020 SYSTEM AND METHODS FOR ZERO-STEP CUSTOMERPROXIMITY DETECTION USING MOBILE DEVICE LOW EMISSIONS BEACONS and isalso a continuation-in-part of: 17/005,038 Aug. 27, 2020 SYSTEM ANDMETHOD FOR THIRD- PARTY FOOD AND DINING ORDERING CONTROL which claimsbenefit of, and priority to: 62/964,413 Jan. 22, 2020 SYSTEM AND METHODFOR THIRD- PARTY FOOD AND DINING ORDERING CONTROL and is also acontinuation-in-part of: 16/796,342 Feb. 20, 2020 ZERO-STEPAUTHENTICATION USING WIRELESS-ENABLED MOBILE DEVICES which claimsbenefit of, and priority to: 62/938,817 Nov. 21, 2019 ZERO-STEPAUTHENTICATION USING WIRELESS-ENABLED MOBILE DEVICES the entirespecification of each of which is incorporated herein by reference.

BACKGROUND Field of the Art

The disclosure relates to the field of automated customer servicesystems, and more particularly to the field of customer proximitydetection and communications using wireless-enabled mobile devices.

Discussion of the State of the Art

Wireless mobile computing devices (e.g., smartphones) have enabledwireless payment technologies wherein the consumer makes a payment byreceiving a payment request on the customer's mobile device andauthorizing the payment by tapping an icon on the screen. However, notechnologies have been widespread and easily adopted for the purposes ofproximity detection and proximity-based messaging to customers, for thepurposes of providing more intimate and accurate communications, bothautomated and manual, to customers, especially in the context of socialdistancing in situations where it is imperative customers remain outsideof certain proximities of other customers and of employees.

What is needed is a system and method for zero-step customer proximitydetection, using mobile devices that nearly all customers already carryon their persons as it is, in a manner that entices customers andrewards them for using the system that provides this functionality,rather than being a hinderance or annoyance to customers.

SUMMARY

Accordingly, the inventor has conceived and reduced to practice, asystem and methods for zero-step customer proximity detection usingmobile device low emissions beacons, which uses a customer mobiledevice, a single or plurality of BLUETOOTH™ low-emissions (BTLE)beacons, a network, a server, and an application that may operateseparately on a mobile device and the single or plurality of BLUETOOTH™low-emissions (BTLE) beacons, which allows businesses to detect knowncustomers that come within a specified proximity of any connected BTLEbeacons, and provide interactions with them on a zero-step and sociallydistanced basis, track their proximity to other customers and staffusing similar applications, manage table assignments, offer deals orprovide incentives to enter or patronize a business establishment.

According to a preferred embodiment, a system for zero-step customerproximity detection using mobile device low emissions beacons isdisclosed, comprising: a database comprising customer information, thecustomer information comprising: a list of registered wireless mobiledevices; a device identifier for each registered wireless mobile device;a photograph of a customer associated with each registered wirelessmobile device; a short-range low-energy wireless network beaconcomprising a first memory, a first processor, and a first plurality ofprogramming instructions stored in the first memory, and operating onthe first processor, wherein the first plurality of programminginstructions, when operating on the processor, cause the paymentfacilitation device to: emit a beacon signal with short-range wirelesscommunications; wherein the beacon signal includes identifyinginformation and application information from the short-range low-energywireless network beacon; receive responses from mobile devices reachedby the emitted beacon signal; communicate with a database comprisingcustomer information to determine the identity of the responding mobiledevice owner; a mobile device comprising a second memory, a secondprocessor, and a second plurality of programming instructions stored inthe second memory, and operating on the second processor, wherein thesecond plurality of programming instructions, when operating on theprocessor, cause the payment facilitation device to: receive a signalemitted by a short-range low-energy wireless network beacon; send thereceived information to a business server; respond to a beacon signalemitted by a short-range low-energy wireless network beacon; wherein theresponse to a beacon signal emitted by a short-range low-energy wirelessnetwork beacon includes information on the relative distance between thetwo devices based on the first received beacon signal; and a businessserver comprising a third memory, a third processor, and a thirdplurality of programming instructions stored in the third memory, andoperating on the third processor, wherein the third plurality ofprogramming instructions, when operating on the third processor, causethe payment facilitation server to: receive identifying information froma mobile device; determine whether or not a matching photograph andother information on a user exists in a database comprising customerinformation exists for the received identifying information; send theinformation from the database comprising customer information thatmatches the received identifying information, to the mobile device thatsent the identifying information; and enable communications with otherconnected mobile devices to inform them of the identity and matchingcustomer information of the mobile device that interacted with thebeacon.

According to another preferred embodiment, a method for zero-stepcustomer proximity detection using mobile device low emissions beaconsis disclosed, comprising the steps of: emitting a beacon signal withshort-range wireless communications, using a short-range low-energywireless network beacon; wherein the beacon signal includes identifyinginformation and application information from the short-range low-energywireless network beacon, using a short-range low-energy wireless networkbeacon; receiving responses from mobile devices reached by the emittedbeacon signal, using a short-range low-energy wireless network beacon;communicating with a database comprising customer information todetermine the identity of the responding mobile device owner, using ashort-range low-energy wireless network beacon; receiving a signalemitted by a short-range low-energy wireless network beacon, using amobile device; sending the received information to a business server,using a mobile device; responding to a beacon signal emitted by ashort-range low-energy wireless network beacon, using a mobile device;wherein the response to a beacon signal emitted by a short-rangelow-energy wireless network beacon includes information on the relativedistance between the two devices based on the first received beaconsignal, using a mobile device; receiving identifying information from amobile device, using a business server; determining whether or not amatching photograph and other information on a user exists in a databasecomprising customer information exists for the received identifyinginformation, using a business server; sending the information from thedatabase comprising customer information that matches the receivedidentifying information, to the mobile device that sent the identifyinginformation, using a business server; and enabling communications withother connected mobile devices to inform them of the identity andmatching customer information of the mobile device that interacted withthe beacon, using a business server.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings illustrate several aspects and, together withthe description, serve to explain the principles of the inventionaccording to the aspects. It will be appreciated by one skilled in theart that the particular arrangements illustrated in the drawings aremerely exemplary, and are not to be considered as limiting of the scopeof the invention or the claims herein in any way.

FIG. 1 is a block diagram illustrating an exemplary system architecturefor a zero-step authentication system.

FIG. 2 is a block diagram illustrating an exemplary architecture for anaspect of zero-step authentication system, the payment facilitationserver.

FIG. 3 is a flow diagram illustrating an exemplary flow of payments inan embodiment.

FIG. 4 is a diagram illustrating an exemplary business/customerinteraction and showing an exemplary screenshot.

FIG. 5 is a diagram illustrating an exemplary bill splitting feature andshowing an exemplary screenshot.

FIG. 6 is a flow diagram showing the steps of an exemplary method forregistration of a customer's mobile device and order placement.

FIG. 7 is a flow diagram showing the steps of an exemplary method forzero-step authentication and completion of a transaction.

FIG. 8 is a flow diagram showing the steps of an exemplary method forestablishment of an account and pre-authorization of payments.

FIG. 9 is a flow diagram showing the steps of an exemplary method forbill splitting among customers.

FIG. 10 is a flow diagram showing the steps of an exemplary method forfunds transfer among customers.

FIG. 11 is a block diagram illustrating an exemplary hardwarearchitecture of a computing device.

FIG. 12 is a block diagram illustrating an exemplary logicalarchitecture for a client device.

FIG. 13 is a block diagram showing an exemplary architecturalarrangement of clients, servers, and external services.

FIG. 14 is another block diagram illustrating an exemplary hardwarearchitecture of a computing device.

FIG. 15 is a system diagram illustrating a system for zero-step customerproximity detection using mobile device low emissions beacons.

FIG. 16 is a system diagram illustrating a system for zero-step customerproximity detection using mobile device low emissions beacons, with abiometric scanner for customer identification.

FIG. 17 is a system diagram illustrating two mobile devices with BTLEtransmitters, receivers, and BTLE-enabled applications, measuring thedistance between each other.

FIG. 18 is a system diagram illustrating multiple BTLE-enabled mobiledevices measuring distances between each other, based on triangulationsof position from overlapping distance values between each device.

FIG. 19 is a system diagram illustrating a user walking within range ofa BTLE-enabled beacon device that may be a mobile device or an affixedbeacon device, connected to a point-of-sale device and a business serverover a network.

FIG. 20 is a method diagram illustrating a customer or patron walkinginto a business establishment, with employee devices acting as BTLEbeacons and receivers to communicate with the customer or patron device.

FIG. 21 is a method diagram illustrating a customer or patron walkingpast a business establishment, with a BTLE beacon or beacons andreceivers communicating with the customer or patron device, such as oneaffixed to a door entryway or near a window facing a sidewalk.

FIG. 22 is a method diagram illustrating a customer or patron walking upto a desk-mounted device such as one mounted in the front of a hotel orother business front-end, to assist or even take the place of a maitre'dand communicate with a customer mobile device.

FIG. 23 is a method diagram illustrating steps in the functionality of aBTLE proximity application.

FIG. 24 is a message flow diagram illustrating messages transferredbetween components in a system for zero-step customer proximitydetection using mobile device low emissions beacons.

DETAILED DESCRIPTION

The inventor has conceived, and reduced to practice, a zero-stepauthentication system and method which uses wireless mobile devices toautomatically make payments in a secure manner without requiring thecustomer to handle his or her mobile device The system and method uses apayment facilitation device at the business location which automaticallydetects and recognizes registered mobile devices, displays a photo ofthe customer to a business employee for identity confirmation, andautomatically deducts payments for purchases from a pre-authorizedcustomer account. The customer account is managed by a paymentprocessing server, which stores the customer account data, makesappropriate deductions, sends confirmation of deductions to thecustomer's mobile device, and automatically refills the customer'saccount by making pre-authorized charges to the customer's bankinginstitution.

Because the customer does not have to focus on his or her mobile device,the customer is free to interact naturally with the business environmentand with employees of the business. For example, the customer is free tolook around to experience the store's ambiance, which will tend tocreate a positive impression on the customer, and increase thelikelihood that the customer will wish to return. Further, the customeris free to look at and speak with the business' employees, whichfacilitates personal interactions and relationships, making the customerfeel more welcome and also increasing the likelihood that the customerwill wish to return. These natural interactions are hindered by thehandling and use of mobile phones, where the customer's attention isdrawn away from the business environment and its employees in order tofocus on the details of making or approving the transaction using his orher mobile device.

While the examples herein primarily discuss authorization of payments,the invention is not limited to authorization of monetary transactions,and can be used for authorization and transfer of any asset, orrepresentation of an asset, that can be transferred electronically, forexample: electronic transfers of real currency (credit card charges,bank transfers and payments, etc.), transfers of blockchain-basedcurrencies such as Bitcoin, and transfers of digitized contracts orpromises to pay or transfer physical assets (including, but not limitedto, IOUs, certificates of ownership of stocks or other securities, anddeeds for real estate).

One or more different aspects may be described in the presentapplication. Further, for one or more of the aspects described herein,numerous alternative arrangements may be described; it should beappreciated that these are presented for illustrative purposes only andare not limiting of the aspects contained herein or the claims presentedherein in any way. One or more of the arrangements may be widelyapplicable to numerous aspects, as may be readily apparent from thedisclosure. In general, arrangements are described in sufficient detailto enable those skilled in the art to practice one or more of theaspects, and it should be appreciated that other arrangements may beutilized and that structural, logical, software, electrical and otherchanges may be made without departing from the scope of the particularaspects. Particular features of one or more of the aspects describedherein may be described with reference to one or more particular aspectsor figures that form a part of the present disclosure, and in which areshown, by way of illustration, specific arrangements of one or more ofthe aspects. It should be appreciated, however, that such features arenot limited to usage in the one or more particular aspects or figureswith reference to which they are described. The present disclosure isneither a literal description of all arrangements of one or more of theaspects nor a listing of features of one or more of the aspects thatmust be present in all arrangements.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only, and are not to betaken as limiting the disclosure in any way.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or morecommunication means or intermediaries, logical or physical.

A description of an aspect with several components in communication witheach other does not imply that all such components are required. To thecontrary, a variety of optional components may be described toillustrate a wide variety of possible aspects and in order to more fullyillustrate one or more aspects. Similarly, although process steps,method steps, algorithms or the like may be described in a sequentialorder, such processes, methods and algorithms may generally beconfigured to work in alternate orders, unless specifically stated tothe contrary. In other words, any sequence or order of steps that may bedescribed in this patent application does not, in and of itself,indicate a requirement that the steps be performed in that order. Thesteps of described processes may be performed in any order practical.Further, some steps may be performed simultaneously despite beingdescribed or implied as occurring non-simultaneously (e.g., because onestep is described after the other step). Moreover, the illustration of aprocess by its depiction in a drawing does not imply that theillustrated process is exclusive of other variations and modificationsthereto, does not imply that the illustrated process or any of its stepsare necessary to one or more of the aspects, and does not imply that theillustrated process is preferred. Also, steps are generally describedonce per aspect, but this does not mean they must occur once, or thatthey may only occur once each time a process, method, or algorithm iscarried out or executed. Some steps may be omitted in some aspects orsome occurrences, or some steps may be executed more than once in agiven aspect or occurrence.

When a single device or article is described herein, it will be readilyapparent that more than one device or article may be used in place of asingle device or article. Similarly, where more than one device orarticle is described herein, it will be readily apparent that a singledevice or article may be used in place of the more than one device orarticle.

The functionality or the features of a device may be alternativelyembodied by one or more other devices that are not explicitly describedas having such functionality or features. Thus, other aspects need notinclude the device itself.

Techniques and mechanisms described or referenced herein will sometimesbe described in singular form for clarity. However, it should beappreciated that particular aspects may include multiple iterations of atechnique or multiple instantiations of a mechanism unless notedotherwise. Process descriptions or blocks in figures should beunderstood as representing modules, segments, or portions of code whichinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Alternate implementations areincluded within the scope of various aspects in which, for example,functions may be executed out of order from that shown or discussed,including substantially concurrently or in reverse order, depending onthe functionality involved, as would be understood by those havingordinary skill in the art.

Definitions

“Business establishment” or “place of business” as used herein mean thelocation of any business entity with which customers may transactbusiness. Typically, this will be a physical location where customersmay enter the location and transact business directly with employees ofthe business, but may also be a business without a physical locationsuch as an online or telephone order retailer. Many examples herein usea restaurant as the business establishment, but the invention is notlimited to use in restaurants, and is applicable to any businessestablishment.

The term “network” as used herein means any communication connectionbetween two or more computing devices, whether such connection is madedirectly (e.g., from one device containing a Bluetooth radio to anotherdevice containing a Bluetooth radio) or through an intermediary devicesuch as a router, where a number of devices connected to the router mayall communicate with one another.

Conceptual Architecture

FIG. 1 is a block diagram illustrating an exemplary system architecture100 for a zero-step authentication system. The primary components of thesystem are a payment facilitation device 103, a unified communicationsdevice or telephony exchange system (UC system) 101, and a paymentfacilitation server 200. Components or services that may connect to orbe accessed by the system include wireless customer mobile devices 102,and payment processors 109. The payment facilitation device 103 is acomputing device located at a business establishment that is connected(wired or wirelessly) to a UC system 101. The payment facilitationdevice 103 may be wired, or wireless, or both, depending on theimplementation of a given embodiment. While a payment facilitationdevice 103 and UC system 101 are specified in this embodiment, it is notrequired that they be precisely in this configuration, and otherconfigurations are possible, including a non-SIP computing deviceconnected to a network without a US system 101. The payment facilitationdevice 103 comprises a screen (not shown) and applications for acustomer information entry portal 104 and a customer identificationconfirmation application 105. The payment facilitation device 103 may bea mobile computing device like a mobile phone or tablet computer or maybe a desktop or tabletop computing device.

The customer information entry portal 104 is an application on thepayment facilitation device 103 that allows an employee of the businessto enter customer details such as name, telephone number, deviceidentifier, bank, debit, or credit card details, payment preferences,and, if necessary, customer account refill limits and customer accountrefill amounts. The device identifier may be any information that allowsthe system to identify the customer mobile device 102, including, butnot limited to, a mobile access control (MAC) address (e.g., a MACaddress for the device's WiFi radio, a MAC address for the device'sBluetooth radio, etc.), the device's 102 serial number, the device'smobile equipment identifier (MEID) or international mobile equipmentidentity (IMEI) number, the integrated circuit card identifier (ICCID)of the subscriber identity module (SIM) card inserted into the customermobile device 102, and the device's 102 secure element identification(SEID) number.

The customer identification and confirmation application 105 is anapplication that provides security in financial transactions by allowingthe employee of the business to visually confirm the identity of thecustomer making a transaction. For example, the payment facilitationdeviceat a particular business location may be connected to multiplecustomer devices simultaneously. The customer identification andconfirmation application 105 may display a photo of the user (customer)of each such connected customer device, and the employee may select thedevice of the customer making the transaction by clicking on thecustomer's photo as displayed by the customer identification andconfirmation application 105 on the payment facilitation device 103.

The UC system 101 is a device or service (e.g., online service) thatintegrates different methods of communication (e.g., phone calls, videocalls, short message service (SMS), instant messaging (chat), email) andallows for all of those different methods of communication to beaccessed through a computing device such as a mobile phone or tabletcomputer. A UC system 101 is the modern, and much more flexible andpowerful, form of a private branch exchange (PBX) telephone equipmentsystem that allowed businesses to connect multiple internal telephonesto a single incoming telephone line. In this example, the UC system 101acts as the interface between the payment facilitation device 103, thecustomer mobile devices 102, and the payment facilitation server 200.

A customer mobile device 102 may be connected to the system via anywireless network connection, for example through the Internet 106, amobile (cellular) network 107, or through a local wireless network 108such as WiFI, Bluetooth, etc. In the case of remote connections such asthose made through the Internet 106 or mobile service 107, the locationof a customer mobile device 102 and its location relative to the paymentfacilitation device 103 or other customer mobile devices 102 may beestablished through use of the device's satellite positioning systemhardware (e.g., GPS, GLONASS, Galileo), by identifying the location ofan intermediary device to which the device is connected (e.g., a WiFirouter, etc. In the case of local connections, which typically use shortrange wireless transmissions, it may not be necessary to determine thelocation of the mobile customer device 102 because the short range ofwireless communications establishes that the payment facilitation device103 or other mobile customer devices are nearby. For example, when usinga Bluetooth Class 2 connection to connect to other devices, it will beapparent that the other devices are nearby because Bluetooth Class 2 hasan effective range on the order of 10 meters.

In a typical scenario, the first time a customer enters a businessestablishment with a customer mobile device 102, an employee of thebusiness establishment will enter the customer's information using thecustomer information entry portal 104 and register the customer mobiledevice 102 using the customer mobile device's 102 identification. When acustomer mobile device 102 enters a business establishment, the paymentfacilitation device 103 and customer mobile device 102 willautomatically detect each other and establish a network connection. Thepayment facilitation device 103 will recognize the customer mobiledevice 102 using the customer mobile device's identifier. As thecustomer makes an order, the business's employee will confirm theidentity of the customer using the customer identification confirmationapplication 105. The payment facilitation device connects to the paymentfacilitation server 200, either directly or through the UC system 101,forwards the customer information and order information to the paymentfacilitation server 200. The payment facilitation server 200, checks thecustomer's account and either deducts and appropriate amount from thecustomer's prepaid account or sends the payment details to a paymentprocessor 109 for processing. Once the payment is processed, the paymentfacilitation server 200 sends a confirmation of the payment either tothe payment facilitation device 103, the customer mobile device 102, orboth. In a scenario where the customer is in a remote location from thebusiness establishment (e.g., a phone order or online order), theprocess is much the same except that the first time customer informationentry and mobile device registration occurs remotely, and the employeedoes not visually identify the customer (although other methods ofidentifying the customer may apply, such as personal identificationnumber (PIN) codes, voice print identification, telephone numberidentification, or customer mobile device 102 identifiers).

FIG. 2 is a block diagram illustrating an exemplary architecture for anaspect of zero-step authentication system, the payment facilitationserver 200. The payment facilitation server 200 manages customerinformation and payments from multiple customers. In this example, thepayment facilitation server comprises a customer information database201, a customer identification engine 202, a payment processing manager209, and one or more applications for managing bill splitting, fundtransfers, and account information. Note that, in some embodiments, thebill splitting and fund transfer applications may be applications on thecustomer mobile device 102 instead of on the payment facilitation server200. As the payment facilitation server receives customer informationand device registrations, it stores them in a customer informationdatabase. Such customer information may comprise customer details suchas name, telephone number, device identifier, bank, debit, or creditcard details, payment preferences, and, if necessary, customer accountrefill limits and customer account refill amounts. The device identifiermay be any information that allows the system to identify the customermobile device 102, including, but not limited to, a mobile accesscontrol (MAC) address (e.g., a MAC address for the device's WiFi radio,a MAC address for the device's Bluetooth radio, etc.), the device's 102serial number, the device's mobile equipment identifier (MEID) orinternational mobile equipment identity (IMEI) number, the integratedcircuit card identifier (ICCID) of the subscriber identity module (SIM)card inserted into the customer mobile device 102, and the device's 102secure element identification (SEID) number.

The customer identification engine 202 provides additional security byconfirming the identity of the customer before processing payments. Inthis example, the customer identification engine 202 has three separateidentification methods, a voiceprint identifier 203, a telephone numberidentifier 204, and a device ID identifier 205. The voiceprintidentifier 203 can provide confirmations of customer identities eitherby matching voice samples of specific words and phrases provided by thecustomer as during account creation and device registration or, in amore sophisticated version, may match the customer's voice to any spokenwords and phrases using machine learning algorithms. The telephonenumber identifier 204 receives caller identification (caller ID)information from the UC system 101, and verifies that the phone numberfrom which the order is being made matches the phone number in thecustomer account information. The device ID identifier 205 receives adevice identifier from the UC system 101 and matches it to the deviceidentifier in the customer database 201 to confirm that the device isregistered. In some embodiments, other methods of identifying thecustomer may be used, for example, PIN codes. In some embodiments, twoor more of these identifiers may be used together to confirm thecustomer's identity.

As customer information and order information is received, the paymentfacilitation server 200 checks the customer's account using the customeraccount management application 208 and either deducts and appropriateamount from the customer's prepaid account or sends the payment detailsto the payment processing manager 209, which forwards the paymentrequest to a payment processor 109 for processing. Once the payment isprocessed, the payment facilitation server 200 sends a confirmation ofthe payment either to the payment facilitation device 103, the customermobile device 102, or both.

The bill splitting application 206 receives a bill that is to be sharedby two or more customers (e.g., a restaurant dining bill), the deviceidentifier of two or more customer mobile devices 102, and provides aninterface for those customers to allocate items on the bill between thecustomers. Once each of the customers involved approves the allocation,the bill splitting application forwards each customer's portion of thebill to the payment processing manager 209 The fund transfer application207 operates in a similar manner for fund transfers between customers.Customers involved in the fund transfer specify amounts to betransferred to other customers, and once approved by all customersinvolved in the fund transfer, the fund transfer application forforwards the approved funds transfers to the payment processing manager209 for execution.

FIG. 3 is a flow diagram illustrating an exemplary flow of payments 300in an embodiment. When a customer 303 authorizes a transaction (whichauthorization may be pre-approved) through his or her customer mobiledevice 102, the payment authorization is sent to the business 302 at thebusiness' payment facilitation device 103. The payment facilitationdevice 103 of the business 302 sends a payment request to the paymentfacilitation server 200. The payment facilitation server 200 checks thecustomer's pre-paid account 304 to determine whether pre-paid funds areavailable. If such funds are available, a deduction is made from thecustomer pre-paid account 304 in the amount of the authorized payment,and a confirmation is confirmed by the payment facilitation server 200.If sufficient funds are not available in the customer pre-paid account,the account is either refilled or a direct payment request is made. Ineither such case, the payment facilitation server 200 sends a paymentrequest to a payment processor 109, which are financial intermediarieslike Visa and Mastercard, who process transactions on behalf offinancial institutions 301 (i.e., banks). The payment processor 109sends the payment request to a financial institution 301 at which thecustomer 303 has an account. The financial institution 301 receives thepayment request, and sends a payment to the payment processor 109,typically along with a transaction fee. The payment processor 109receives the payment and transaction fee, and forwards the payment tothe payment facilitation server along with a portion of the transactionfee. The payment facilitation server 200 forwards the payment to thebusiness 302, which forwards a confirmation of payment 303 to thecustomer, completing the transaction.

Detailed Description of Exemplary Aspects

FIG. 4 is a diagram illustrating an exemplary business/customerinteraction 400 and showing an exemplary screenshot. In this example, acustomer 401 (who already has an account and registered device 402 at abusiness establishment) makes an order. The customer's device 402 andthe payment facilitation device 103 detect each other and establish aconnection when the customer 401 enters the business establishment. Thecustomer's photograph 403 is displayed on the business' paymentfacilitation device 103, along with the customer's information 404 andorder details 405. An employee of the business clicks on the customerphotograph 403 to confirm the identity of the customer 401. Onceconfirmed, the customer device 402 automatically approves payment andreceives confirmation of the payment without the customer having thehandle the device 402. The customer device 402 may remain in thecustomer's pocket, purse, backpack, etc., and does not have to beremoved to complete the transaction.

FIG. 5 is a diagram illustrating an exemplary bill splitting feature 500and showing an exemplary screenshot. In this example, three customers,Bob 501, Sally 503, and Joe 505, each with their respective mobiledevices 502, 504, and 506, have a meal together at a restaurant and wantto split the bill among themselves. Each customer's mobile device has abill splitting application installed on it, which shows a copy of thebill and the customers who dined together. For example, Bob's 501 mobiledevice 502 shows the bill information 507 for the group on the left-handside of his screen, and a window for himself 508, a window for Sally509, and window for Joe 510 on the right side. The mobile devices 504,506 of Sally 503 and Joe 505 show similar screens. The windows 508, 509,510, each show a photo (or other representation) of the customer, aspace for allocating items from the bill, and a total of the itemsallocated to that customer. As each customer, on his or her respectivemobile device 502, 504, 506, allocates food and drink items from thebill information 507 by clicking on them and dragging them to the windowof a person on the right, the allocation of those food and drink itemsappears in the window of the person to whom the item has been allocated,as indicated by the arrows. For example, the risotto Milanese and whitewine have been allocated to Bob (either by Bob or by one of the othertwo customers), a total due from Bob of $26 is shown, and thisinformation is updated on all three mobile devices 502, 504, 506. Onceall three customers 501, 503, 505 approve the allocation, each person'smobile device 502, 504, 506 processes the payment for the amountallocated to that customer. In some embodiments, unallocated items maybe automatically split among the customers in the group.

FIG. 6 is a flow diagram showing the steps of an exemplary method forregistration of a customer's mobile device and order placement. When acustomer calls restaurant a first time to place an order 601, thecustomer's telephone number is captured using UC telephony equipment,and additional customer information is gathered and entered intodatabase by an employee of the business 602. The customer than makes hisor her order and the order is completed 603. Each time the customermakes a subsequent call to same business to place an order 604, thecustomer's telephone number is captured using UC telephone equipment,and the customer's information is retrieved from a customer databaseusing a customer identification application 605. The customer than makeshis or her order and the order is completed 606 without the customerhaving to provide his or her information. The same procedure is usedwhen a customer physically enters a business establishment, except thatthe registration is performed in person.

FIG. 7 is a flow diagram showing the steps of an exemplary method forzero-step authentication and completion of a transaction. When acustomer enters a business establishment 701, the customer's wirelessdevice and business payment facilitation devicedetect each other andautomatically establish connection 702. The business paymentfacilitation deviceretrieves the customer device identifier (ID) anduses the customer device ID to retrieve customer information fromcustomer information database located on a payment facilitation server703. The business payment facilitation devicedisplays customer's photoand information to a restaurant employee, who confirms customer'sidentity by clicking on the photo of the customer 704. The customer theplaces an order 705. When the order is placed, the business paymentfacilitation devicesends payment details to payment facilitation server,which either deducts amount from customer's pre-paid account balance orsends charge to payment processors 706. Optionally, an additionalsecurity step may be inserted wherein the customer's wireless devicereceives and displays a request for confirmation of the order from thebusiness CIP device and the customer clicks on the displayed request toconfirm the order 707. Finally, the customer's order is completed 708.

FIG. 8 is a flow diagram showing the steps of an exemplary method forestablishment of an account and pre-authorization of payments. First, acustomer establishes and account using his or her customer mobile deviceand provides payment details (e.g., credit card, debit card, bankdetails for ACH, etc.) 801. The customer then sets automatic an accountpayment limit, a refill limit, and a refill amount 802. For example, thecustomer may set a payment limit for each transaction at $50, a refilllimit (i.e., minimum account balance below which the account will beautomatically refilled) of $10, and a refill amount of $100. Thecustomer may choose to have such payments sent automatically withouthandling his or her mobile device (zero-step authentication) 803 or maychoose to authorize each payment individually using his or her mobiledevice 804. A customer account management application funds the accountin the amount of the refill amount using payment details 805. Thus, inthis example, the customer has pre-authorized payments of up to $50 pertransaction, and pre-authorized the system to automatically refill hisaccount from the customer's financial institution (or credit card) inthe amount of $100 whenever the account balance falls below $10. Whenthe customer places an order, the customer account managementapplication checks account balance, deducts an amount equal to the orderfor the order (after confirmation, if required), and refills accountbalance using payment information if the account balance falls below therefill limit 806.

FIG. 9 is a flow diagram showing the steps of an exemplary method forbill splitting among customers. Each customer mobile device runs anapplication that shows nearby customer devices also using the paymentsystem 901. Customers dining together form a group by selecting oneanother (or accepting a group formation created by one or more of them)902. Each customer's device displays a copy of the itemized bill on oneside of the screen, and a photo (or other representational image) ofeach other customer in the group on the other side of the screen 903.One or more of the customers in the group assigns payment by clickingand dragging items from the itemized bill to the photo (or image) of thecustomer responsible for paying for that item 904. When the group isfinished assigning payments, each customer approves his/her proposedpayment assignments, with unassigned items being distributed equallyamong the customers in the group 905. After all customers in the grouphave approved their payment assignments, the payment system processespayments from each customer's account according to the approved paymentassignments 906.

FIG. 10 is a flow diagram showing the steps of an exemplary method forfunds transfer among customers. Each customer mobile device runs anapplication that shows nearby customer devices also using the paymentsystem 1001. Customers wishing to exchange funds form a group byselecting one another (or accepting a group formation created by one ormore of them) 1002. Each customer's device displays a photo (or otherrepresentational image) of each other customer in the group 1003. One ormore of the customers in the group proposes a fund transfer by clickingand dragging from one customer to another, creating an arrow betweenthat pair of customers in the group indicating a direction of transfer,and enters an amount of funds to be transferred 1004. When the group isfinished proposing fund transfers, each customer approves his/herproposed fund transfer(s) 1005. After all customers in the group haveapproved their proposed transfers, the payment system processes paymentsfrom each customer's account according to the approved fund transfers1006.

FIG. 15 is a system diagram illustrating a system for zero-step customerproximity detection using mobile device low emissions beacons. A mobiledevice 1501 exists, such as a smartphone, PDA, tablet, or other device,which may run an operating system including IOS™, WINDOWS MOBILE™,ANDROID™, and potentially others, and which may be in the possession ofa customer or business client. The mobile device 1501 is connected to,or has built into it, a BLUETOOTH™ Low Emissions (“BTLE”) transmitterand receiver 1502, and an application that is configured to utilize sucha transmitter/receiver 1503. Such an application may be written in avariety of programming languages, such as C, C++, C#, JAVA™, or others.The application may be written in a general-purpose manner to interactwith any business BTLE beacon or mobile device acting as a beacon, suchas a plurality of mobile devices operated by a business 1505, and mayeither maintain a local memory store of recognized and known businesses(which may be treated differently than unknown business beacons) or mayconnect to a network 1510 and server 1520 to determine of a business'supplied information over BTLE transmitter and receiver communicationsis legitimate. Business mobile devices 1505 may represent a plurality ofdevices such as smartphones, PDAs, tablets, or other devices, which donot necessarily need to all of one device type, which may run operatingsystems including IOS™, WINDOWS MOBILE™, ANDROID™, and potentiallyothers, each of which possesses a BTLE transmitter and receiver 1506 anda business-side application configured to utilize the BTLEtransmitter/receiver 1507. The business-side application may be the sameapplication as the one operating on the client or customer device ordevices 1503, merely configured differently, or it may be a separateapplication that merely is capable of interacting with the client-sideapplication 1503. A business-side application 1507 is capable ofcommunicating with a network 1510 over either a BTLEtransmitter/receiver 1506, or over another form of transmitter/receiversuch as WIFI™ or cellular data, to communicate with a network-connectedserver 1520 and a point-of-sale (“POS”) system 1540. The purpose of thebusiness-side application's 1507 communications with the server 1520 andPOS 1540 are to both manage and interact with the business' items forsale and their inventory management, if any, and to interact with aserver 1520 hosting a customer database 1530 for the purposes ofidentifying, retrieving, and saving customer information to providepersonalized interactions with customer or client-side applications1503. Such a system may also be used for zero-step authentication, forreturning or known customers or clients. Such communications may occurover a local area network, the internet, or some other wide areanetwork, and the server 1520 and customer database 1530 may be hostedeither locally or remotely, or exist in a cloud infrastructure. A mobiledevice 1501 with the client application 1503 may communicate over anetwork 1510 or directly with a business device or devices 1505 and thebusiness-side application 1507 to establish an initial point of contact,identify a customer if possible, calculate their proximity based on theenergy levels of the signal transmissions to and from the user andbusiness device or devices, and with a plurality of devices withdifferent positioning sharing their proximity data, it is possible tocalculate a user's location relative to the devices within or near abusiness, for purposes such as enforcing social distancing, managingtable assignments in a restaurant, ensuring that there is an evendistribution of employees on a business floor relative to customerpositions and routing, and even apply machine learning to customerroutes through a business to determine what paths customers may seem totake such as in retail outlets, to maximize their revenue potential byplacing products in a manner along the route designed to enticecustomers more effectively to purchase them.

FIG. 16 is a system diagram illustrating a system for zero-step customerproximity detection using mobile device low emissions beacons, with abiometric scanner for customer identification. A mobile device 1501exists, such as a smartphone, PDA, tablet, or other device, which mayrun an operating system including IOS™, WINDOWS MOBILE™, ANDROID™, andpotentially others, and which may be in the possession of a customer orbusiness client. The mobile device 1501 is connected to, or has builtinto it, a BLUETOOTH™ Low Emissions (“BTLE”) transmitter and receiver1502, and an application that is configured to utilize such atransmitter/receiver 1503. Such an application may be written in avariety of programming languages, such as C, C++, C#, JAVA™, or others.The application may be written in a general-purpose manner to interactwith any business BTLE beacon or mobile device acting as a beacon, suchas a plurality of mobile devices operated by a business 1505, and mayeither maintain a local memory store of recognized and known businesses(which may be treated differently than unknown business beacons) or mayconnect to a network 1510 and server 1520 to determine of a business'supplied information over BTLE transmitter and receiver communicationsis legitimate. Business mobile devices 1505 may represent a plurality ofdevices such as smartphones, PDAs, tablets, or other devices, which donot necessarily need to all of one device type, which may run operatingsystems including IOS™, WINDOWS MOBILE™, ANDROID™, and potentiallyothers, each of which possesses a BTLE transmitter and receiver 1506 anda business-side application configured to utilize the BTLEtransmitter/receiver 1507. The business-side application may be the sameapplication as the one operating on the client or customer device ordevices 1503, merely configured differently, or it may be a separateapplication that merely is capable of interacting with the client-sideapplication 1503. A business-side application 1507 is capable ofcommunicating with a network 1510 over either a BTLEtransmitter/receiver 1506, or over another form of transmitter/receiversuch as WIFI™ or cellular data, to communicate with a network-connectedserver 1520 and a point-of-sale (“POS”) system 1540. The purpose of thebusiness-side application's 1507 communications with the server 1520 andPOS 1540 are to both manage and interact with the business' items forsale and their inventory management, if any, and to interact with aserver 1520 hosting a customer database 1530 for the purposes ofidentifying, retrieving, and saving customer information to providepersonalized interactions with customer or client-side applications1503. Such a system may also be used for zero-step authentication, forreturning or known customers or clients. Such communications may occurover a local area network, the internet, or some other wide areanetwork, and the server 1520 and customer database 1530 may be hostedeither locally or remotely, or exist in a cloud infrastructure. A mobiledevice 1501 with the client application 1503 may communicate over anetwork 1510 or directly with a business device or devices 1505 and thebusiness-side application 1507 to establish an initial point of contact,identify a customer if possible, calculate their proximity based on theenergy levels of the signal transmissions to and from the user andbusiness device or devices, and with a plurality of devices withdifferent positioning sharing their proximity data, it is possible tocalculate a user's location relative to the devices within or near abusiness, for purposes such as enforcing social distancing, managingtable assignments in a restaurant, ensuring that there is an evendistribution of employees on a business floor relative to customerpositions and routing, and even apply machine learning to customerroutes through a business to determine what paths customers may seem totake such as in retail outlets, to maximize their revenue potential byplacing products in a manner along the route designed to enticecustomers more effectively to purchase them.

According to an embodiment, a customer 1610 may walk near or into abusiness establishment that operates a biometric scanner 1620, which maybe any one of, or a combination of, a fingerprint scanner, iris scanner,facial recognition scanner, voice scanner, or other biometric scanner toidentify individuals, for either one-step or zero-step authentication,supplementing or replacing the authentication steps taken by acustomer's application 1503.

FIG. 17 is a system diagram illustrating two mobile devices with BTLEtransmitters, receivers, and BTLE-enabled applications, measuring thedistance between each other. Two mobile devices 1711, 1721 exist, suchas smartphones, PDAs, tablets, or other devices, which may run anoperating system including IOS™, WINDOWS MOBILE™, ANDROID™, andpotentially others, and which may be in the possession of a customer orbusiness client, and a business employee or be affixes to a part of abusiness such as a desk. Each mobile device 1711, 1721 is connected to,or has built into it, a BLUETOOTH™ Low Emissions (“BTLE”) transmitterand receiver 1712, 1722, and an application that is configured toutilize such a transmitter/receiver 1713, 1723. Such an application maybe written in a variety of programming languages, such as C, C++, C#,JAVA™, or others. The application may be written in a general-purposemanner to interact with any business or customer BTLE beacon or mobiledevice acting as a beacon, such as a plurality of mobile devicesoperated by a business. Business mobile devices may represent aplurality of devices such as smartphones, PDAs, tablets, or otherdevices, which do not necessarily need to all of one device type, whichmay run operating systems including IOS™, WINDOWS MOBILE™, ANDROID™, andpotentially others, each of which possesses a BTLE transmitter andreceiver 1712, 1722 and an application configured to utilize the BTLEtransmitter/receiver 1713, 1723. Each device has an operating range1710, 1720 for their BTLE transmitter/receiver to operate, and when adevice crosses into this threshold, it may receive a beacon transmissionfrom another device, and they may transmit communications with eachother. The strength of the signal and other signal characteristics maybe measured to determine a rough approximation of the distance betweenthe devices.

FIG. 18 is a system diagram illustrating multiple BTLE-enabled mobiledevices measuring distances between each other, based on triangulationsof position from overlapping distance values between each device.

A plurality of mobile devices 1810, 1820, 1830, 1840 exist, such assmartphones, PDAs, tablets, or other devices, which may run an operatingsystem including IOS™, WINDOWS MOBILE™, ANDROID™, and potentiallyothers. Each mobile device 1810, 1820, 1830, 1840 is connected to, orhas built into it, a BLUETOOTH™ Low Emissions (“BTLE”) transmitter andreceiver, and an application that is configured to utilize such atransmitter/receiver. Each device has an operating range for their BTLEtransmitter/receiver to operate, and when a device crosses into thisthreshold, it may receive a beacon transmission from another device, andthey may transmit communications with each other. The strength of thesignal and other signal characteristics may be measured to determine arough approximation of the distance between the devices.

Using a plurality of devices each with other devices in range of eachother, but with different detected distances between them, as shown,triangulation of a target device may be possible, such as through theuse of multiple overlapping distance circles centered on each device,similar to the method by which the epicenter of earthquakes may bedetected by multiple detection stations at different points, bycalculating how far away the epicenter was from each of the stations, inwhich case, with 3 or more stations, only one possible point could bethe center.

FIG. 19 is a system diagram illustrating a user walking within range ofa BTLE-enabled beacon device that may be a mobile device or an affixedbeacon device, connected to a point-of-sale device and a business serverover a network. A customer 1910 with a mobile device exists and walkswithin range of a BTLE beacon 1930, in which the customer mobile deviceand beacon may both or either be a smartphone, PDA, tablet, or otherdevice, which may run an operating system including IOS™, WINDOWSMOBILE™, ANDROID™, and potentially others, and which may be in thepossession of a customer or business client. The mobile device andbeacon both are connected to, or have built into themselves, a BTLEtransmitter and receiver 1931, and an application that is configured toutilize such a transmitter/receiver 1932. Such an application may bewritten in a variety of programming languages, such as C, C++, C#,JAVA™, or others. The application may be written in a general-purposemanner to interact with any business BTLE beacon or mobile device actingas a beacon, and may be capable of communicating with a network 1920over either a BTLE transmitter/receiver 1931, or over another form oftransmitter/receiver such as WIFI™ or cellular data, to communicate witha network-connected server 1940 and a point-of-sale (“POS”) system 1960.The purpose of the business-side application's 1932 communications withthe server 1940 and POS 1960 are to both manage and interact with thebusiness' items for sale and their inventory management, if any, and tointeract with a server 1940 hosting a customer database 1950 for thepurposes of identifying, retrieving, and saving customer information toprovide personalized interactions with customer or client-sideapplications. Such a system may also be used for zero-stepauthentication, for returning or known customers or clients. Suchcommunications may occur over a local area network, the internet, orsome other wide area network, and the server 1940 and customer database1950 may be hosted either locally or remotely, or exist in a cloudinfrastructure. A mobile device with the client application maycommunicate over a network 1920 or directly with a business beacon 1930and the business-side application 1932 to establish an initial point ofcontact, identify a customer if possible, calculate their proximitybased on the energy levels of the signal transmissions to and from theuser and business device or devices, and with a plurality of deviceswith different positioning sharing their proximity data, it is possibleto calculate a user's location relative to the devices within or near abusiness, for purposes such as enforcing social distancing, managingtable assignments in a restaurant, ensuring that there is an evendistribution of employees on a business floor relative to customerpositions and routing, and even apply machine learning to customerroutes through a business to determine what paths customers may seem totake such as in retail outlets, to maximize their revenue potential byplacing products in a manner along the route designed to enticecustomers more effectively to purchase them.

According to the embodiment, a customer may walk past a business with abeacon 1930 affixed near the area where the customer may be walking, inorder to detect the customer and potentially provide incentives viatheir mobile device to enter the business. Other uses for such a systemmay be apparent such as analytics for recognized customers that walkpast the business at certain hours or in relation to certain changes inthe business.

FIG. 20 is a method diagram illustrating a customer or patron walkinginto a business establishment, with employee devices acting as BTLEbeacons and receivers to communicate with the customer or patron device.A customer first may walk into a business establishment 2010, such as arestaurant, retail outlet, hotel, or other business, before abusiness-operated BTLE beacon pings customer mobile device with businessinfo 2020. Such a BTLE beacon may be a mounted or affixed device such asbuilt into the ceiling, built into a wall or walls, affixed to a desk,or it may be a mobile device with a BTLE transmitter and receiver andthe associated application for driving the transmitter/receiver. Thecustomer mobile device application may respond to the beacon ping withidentifying info if the beacon is properly credentialed 2030, from thecustomer's own BTLE transmitter/receiver. Proper business beaconcredentials may be something stored locally on the customer mobiledevice, or it may be stored on a server or cloud service that theapplication may communicate with over a network such as the Internet,and may be a defined set of credentials or a hash key that is defined bythe application or application provider. The business BTLE beacon mayforward any received customer info to a server or servers, or cloudservice, to identify the customer, if they are a repeat-customer andknown to the service 2040. A brand-new customer who has never used theapplication before, or who has not used the application with thisbusiness before, may not be able to be identified, but as a new customertheir identity within the application may be saved such as a hash oftheir username or other identifying information in compliance with localregulations and laws surrounding personal information, and theirpreferences and habits in the business may be saved as well throughouttheir interaction in the business. If they are identified, the businessBTLE beacon or beacons may forward information such as menu data forno-contact ordering, table assignment, reservation information for ahotel, or other business information that may be of interest to thecustomer, to the customer mobile device 2050, while the customerproximity to other customers, to employees, and to certain parts of thebusiness may be monitored with a plurality of business BTLE beacons, sothat customers or employees notified if they are too close, managingsoftware or human managing staff may use proximity data to managerestaurant more effectively, and other functionality may be providedthat requires use of proximity-based data 2060. Customer orders,requests, and other data input from the customer that is relevant to thebusiness, may be sent from the client-side application to the BTLEbeacon or beacons, which may be handled by the business point-of-saleand further sent to the server maintaining customer identification andusage data, to update the customer profile in the database, includingrecording any possible notes about the customer proximity if applicable2070, such as notes about the customer's route through the business ortheir proclivity for being near others or responding well to certainproximity-based dynamics in the business.

FIG. 21 is a method diagram illustrating a customer or patron walkingpast a business establishment, with a BTLE beacon or beacons andreceivers communicating with the customer or patron device, such as oneaffixed to a door entryway or near a window facing a sidewalk. Acustomer first may walk near or walk past a business establishment 2110,such as a restaurant, retail outlet, hotel, or other business, before abusiness-operated BTLE beacon pings customer mobile device with businessinfo 2120. Such a BTLE beacon may be a mounted or affixed device such asbuilt into the ceiling, built into a wall or walls, affixed to a desk,affixed to a door or by a window to reach customers outside of thebusiness, or it may be a mobile device with a BTLE transmitter andreceiver and the associated application for driving thetransmitter/receiver. The customer mobile device application may respondto the beacon ping with identifying info if the beacon is properlycredentialed 2130, from the customer's own BTLE transmitter/receiver.Proper business beacon credentials may be something stored locally onthe customer mobile device, or it may be stored on a server or cloudservice that the application may communicate with over a network such asthe Internet, and may be a defined set of credentials or a hash key thatis defined by the application or application provider. The business BTLEbeacon may forward any received customer info to a server or servers, orcloud service, to identify the customer, if they are a repeat-customerand known to the service 2140. A brand-new customer who has never usedthe application before, or who has not used the application with thisbusiness before, may not be able to be identified, but as a new customertheir identity within the application may be saved such as a hash oftheir username or other identifying information in compliance with localregulations and laws surrounding personal information, and theirpreferences and habits in the business may be saved as well throughouttheir interaction in the business. If they are identified, the businessBTLE beacon or beacons may forward information such as incentives toenter the business, such as coupons, announcements of sales, specialitems the customer might be known to enjoy based on their prior datawith the business, or other such data to attempt to gain the prospectivecustomer, to the customer mobile device 2150. A customer's entry, orfailure to enter the business, and the rate of response for a sample ofcustomers, may be sent by the BTLE beacon via their application to alocal, internet, or cloud server to be recorded for data analytics 2160,including which methods of communicating to the customer via beacon weresuccessful and which were not.

FIG. 22 is a method diagram illustrating a customer or patron walking upto a desk-mounted device such as one mounted in the front of a hotel orother business front-end, to assist or even take the place of a maitre'dand communicate with a customer mobile device.

A customer first may walk into a business establishment 2210, such as arestaurant, retail outlet, hotel, or other business, before abusiness-operated BTLE beacon pings customer mobile device with businessinfo 2220. Such a BTLE beacon may be a mounted or affixed device such asbuilt into the ceiling, built into a wall or walls, affixed to a desk,or it may be a mobile device with a BTLE transmitter and receiver andthe associated application for driving the transmitter/receiver. Thecustomer mobile device application may respond to the beacon ping withidentifying info if the beacon is properly credentialed 2230, from thecustomer's own BTLE transmitter/receiver. Proper business beaconcredentials may be something stored locally on the customer mobiledevice, or it may be stored on a server or cloud service that theapplication may communicate with over a network such as the Internet,and may be a defined set of credentials or a hash key that is defined bythe application or application provider. A desk or table-affixed BTLEbeacon, which may take the place of, or supplement and aid, a maitre'dsuch as at a hotel or a similar front-of-business manager for othertypes of establishments, may forward any received customer info to alocal or remote server to identify the customer, if they are arepeat-customer and known to the service 2240. They A brand-new customerwho has never used the application before, or who has not used theapplication with this business before, may not be able to be identified,but as a new customer their identity within the application may be savedsuch as a hash of their username or other identifying information incompliance with local regulations and laws surrounding personalinformation, and their preferences and habits in the business may besaved as well throughout their interaction in the business. If they areidentified, the business BTLE beacon or beacons may forward informationsuch as menu data for no-contact ordering, table assignment, reservationinformation for a hotel, or other business information that may be ofinterest to the customer, to the customer mobile device 2250, while thecustomer proximity to other customers, to employees, and to certainparts of the business may be monitored with a plurality of business BTLEbeacons, so that customers or employees notified if they are too close,managing software or human managing staff may use proximity data tomanage restaurant more effectively, and other functionality may beprovided that requires use of proximity-based data 2260. Customerorders, requests, and other data input from the customer that isrelevant to the business, may be sent from the client-side applicationto the BTLE beacon or beacons, which may be handled by the businesspoint-of-sale and further sent to the server maintaining customeridentification and usage data, to update the customer profile in thedatabase, including recording any possible notes about the customerproximity if applicable 2270, such as notes about the customer's routethrough the business or their proclivity for being near others orresponding well to certain proximity-based dynamics in the business.

FIG. 23 is a method diagram illustrating steps in the functionality of aBTLE proximity application. A business-side application may beconfigured either from the application itself, or from a web portal orother application configuration tool, or from within the applicationitself with the configuration being copied over to other businessdevices. Such a business application may transmit periodic or continuousBTLE beacon signals via a BTLE transmitter 2310, essentially polling forin-range customer applications to respond to the signal. A customer-sideapplication, which may also be configured to the customer's liking ontheir mobile device, may listen for beacon signals via a BTLE receiver2320, while a mobile device is either being used or while it is idlesuch as in a pocket while the customer may be walking or sitting at atable. The customer-side application receives a business application'sBTLE signal, and may verify that the signal comes from a recognized orlegitimate business rather than i.e. from a hacker or glitch, andresponds via transmitter 2330 to let the beacon know it has reached acustomer. The validation process may take the form of checking thedevice's local storage for data on the business in question, or checkinga server or cloud service for validation of the business, or thebusiness may broadcast a hash that verifies it as legitimate with theclient application even if the client application has never encounteredthe business before, such as with a piece of secure data that theapplication knows can only be generated by legitimate business BTLEbeacon applications. The response may include basic customer identifyinginformation if enabled and permitted by the user of the application, atwhich point the business-side application may receive the customer-sideapplication's response, and attempt to verify the customer identity ifpossible 2340, either with local storage of customer information or witha remote server that has access to a database of customer information,including identifying information. Such a database may be a SQL™ orNOSQL™ database format, such as MONGODB™, and identifying informationcould for instance take the form of a user's password hash and theirusername with the application, which may be checked against the databaserecords securely. If the customer's identity is able to be verified, thebusiness-side application may forward any business specified data to thecustomer's application over the BTLE signal connection, such as coupons,notices about special sales or pricings, new inventory, and otherbusiness messages that may be specified by the business itself 2350. Forproximity-based uses, the customer's distance from the first beacon thatsuccessfully communicated with the customer calculated 2360, based onthe signal strength received from the customer, allowing for otherbeacons to further communicate with each other if the customer comeswithin range to triangulate the customer's location relative to thebeacons with high accuracy 2370. The beacons, whether affixed or beinghosted on mobile devices such as smartphones in use by employees, mayissue to the customer various proximity-based notices, such as tableassignments if they're close enough to be considered “inside” arestaurant, or warnings to keep a certain distance to other customers orstaff 2380, or their proximity data may be used for analytics by thebusiness.

FIG. 24 is a message flow diagram illustrating messages transferredbetween components in a system for zero-step customer proximitydetection using mobile device low emissions beacons. At least two mobiledevices exist, such as a smartphone, PDA, tablet, or other device, whichmay run an operating system including IOS™, WINDOWS MOBILE™, ANDROID™,and potentially others, and which may be in the possession of a customeror business client. The mobile devices are each connected to, or havebuilt into them, individual BLUETOOTH™ Low Emissions (“BTLE”)transmitters and receivers 1502, 1506, and an application that isconfigured to utilize such a transmitter/receiver 1503, 1507. Such anapplication may be written in a variety of programming languages, suchas C, C++, C#, JAVA™, or others. The application may be written in ageneral-purpose manner to interact with any business BTLE beacon ormobile device acting as a beacon, such as a plurality of mobile devicesoperated by a business 1505, and may either maintain a local memorystore of recognized and known businesses (which may be treateddifferently than unknown business beacons) or may connect to a networkand server 1520 to determine of a business' supplied information overBTLE transmitter and receiver communications is legitimate. Businessmobile devices may represent a plurality of devices such as smartphones,PDAs, tablets, or other devices, which do not necessarily need to all ofone device type, which may run operating systems including IOS™, WINDOWSMOBILE™, ANDROID™, and potentially others, each of which possesses aBTLE transmitter and receiver 1506 and a business-side applicationconfigured to utilize the BTLE transmitter/receiver 1507.

As a possible first step in the flow of messages between thesecomponents, a business-side BTLE application 1507 forwards a data pingto its own transmitter/receiver 1506, to a customer's receiver 1502,which is then interpreted by the customer's application 1503, 2410. Sucha data ping could simply be encoded or encrypted business-identifyinginformation, which only a customer application 1503 could unencode ordecrypt and properly validate, but which would be useless tointercepters. A customer application 1503 makes a response message,which is sent to its own transmitter 1502, to the beacon's receiver1506, and interpreted by the beacon's application 1507, with thecustomer's information 2420, which may be identifying information suchas a username and password hash, just a username, the customer's realname, or some other singular or combination of identifying information,and may include preference information relevant to the business ifspecified by the user. The business application 1507 may make a customerverification or identification call 2430 across a local area or widearea network to a server 1520 that may be able to determine in aconnected database whether the customer is who they claim to be, and ifthere is any relevant data on the customer such as known preferences orhabits that the business applications should be aware of, such as whichcoupons to entice a customer with. Any information on the customer thatthe server 1520 is able to verify and access is sent to the businessapplication 1507, 2440. The business application 1507 then transmits tothe customer application 1503 any business-specific data that thebusiness application may determine is relevant to the customer 2450. Forexample, the business application may be told by the server 1520 thatthe customer has been to the business, such as a café, before, andordered a slice of cheesecake. The business application may then offerthe customer 10% off a slice of cheesecake as an informal loyaltyreward, or may simply mention that they have a new variety or flavor ofcheesecake available to order now, to entice the customer or providebetter automated customer service. A customer application 1503 may thenrespond to a previous data transmission by the business application1507, or send its own transmission regardless of a previous transmissionfrom a business application 1507, such as a menu choice for no-contactmenu ordering, setting reservations at a hotel, or responding to couponsoffered by the business application 2460. A variety of proximity-basedalerts and data transmissions may be possible from the businessapplication 1507 to the client application 1503, 2470, such as tellingthem which table is theirs, letting them see where the nearest staffmember is on a map of the business floor, warning them of theirproximity to perhaps other customers or a fire exit, and more.

Many possible uses for proximity data and proximity-time-series dataexist for businesses, and it will be apparent to many with average skillin the art that this system may be used for several other purposes usingthe same configuration and methods as described herein, for analytics,customer service, and more.

Hardware Architecture

Generally, the techniques disclosed herein may be implemented onhardware or a combination of software and hardware. For example, theymay be implemented in an operating system kernel, in a separate userprocess, in a library package bound into network applications, on aspecially constructed machine, on an application-specific integratedcircuit (ASIC), or on a network interface card.

Software/hardware hybrid implementations of at least some of the aspectsdisclosed herein may be implemented on a programmable network-residentmachine (which should be understood to include intermittently connectednetwork-aware machines) selectively activated or reconfigured by acomputer program stored in memory. Such network devices may havemultiple network interfaces that may be configured or designed toutilize different types of network communication protocols. A generalarchitecture for some of these machines may be described herein in orderto illustrate one or more exemplary means by which a given unit offunctionality may be implemented. According to specific aspects, atleast some of the features or functionalities of the various aspectsdisclosed herein may be implemented on one or more general-purposecomputers associated with one or more networks, such as for example anend-user computer system, a client computer, a network server or otherserver system, a mobile computing device (e.g., tablet computing device,mobile phone, smartphone, laptop, or other appropriate computingdevice), a consumer electronic device, a music player, or any othersuitable electronic device, router, switch, or other suitable device, orany combination thereof. In at least some aspects, at least some of thefeatures or functionalities of the various aspects disclosed herein maybe implemented in one or more virtualized computing environments (e.g.,network computing clouds, virtual machines hosted on one or morephysical computing machines, or other appropriate virtual environments).

Referring now to FIG. 11, there is shown a block diagram depicting anexemplary computing device 10 suitable for implementing at least aportion of the features or functionalities disclosed herein. Computingdevice 10 may be, for example, any one of the computing machines listedin the previous paragraph, or indeed any other electronic device capableof executing software- or hardware-based instructions according to oneor more programs stored in memory. Computing device 10 may be configuredto communicate with a plurality of other computing devices, such asclients or servers, over communications networks such as a wide areanetwork a metropolitan area network, a local area network, a wirelessnetwork, the Internet, or any other network, using known protocols forsuch communication, whether wireless or wired.

In one aspect, computing device 10 includes one or more centralprocessing units (CPU) 12, one or more interfaces 15, and one or morebusses 14 (such as a peripheral component interconnect (PCI) bus). Whenacting under the control of appropriate software or firmware, CPU 12 maybe responsible for implementing specific functions associated with thefunctions of a specifically configured computing device or machine. Forexample, in at least one aspect, a computing device 10 may be configuredor designed to function as a server system utilizing CPU 12, localmemory 11 and/or remote memory 16, and interface(s) 15. In at least oneaspect, CPU 12 may be caused to perform one or more of the differenttypes of functions and/or operations under the control of softwaremodules or components, which for example, may include an operatingsystem and any appropriate applications software, drivers, and the like.

CPU 12 may include one or more processors 13 such as, for example, aprocessor from one of the Intel, ARM, Qualcomm, and AMD families ofmicroprocessors. In some aspects, processors 13 may include speciallydesigned hardware such as application-specific integrated circuits(ASICs), electrically erasable programmable read-only memories(EEPROMs), field-programmable gate arrays (FPGAs), and so forth, forcontrolling operations of computing device 10. In a particular aspect, alocal memory 11 (such as non-volatile random access memory (RAM) and/orread-only memory (ROM), including for example one or more levels ofcached memory) may also form part of CPU 12. However, there are manydifferent ways in which memory may be coupled to system 10. Memory 11may be used for a variety of purposes such as, for example, cachingand/or storing data, programming instructions, and the like. It shouldbe further appreciated that CPU 12 may be one of a variety ofsystem-on-a-chip (SOC) type hardware that may include additionalhardware such as memory or graphics processing chips, such as a QUALCOMMSNAPDRAGON™ or SAMSUNG EXYNOS™ CPU as are becoming increasingly commonin the art, such as for use in mobile devices or integrated devices.

As used herein, the term “processor” is not limited merely to thoseintegrated circuits referred to in the art as a processor, a mobileprocessor, or a microprocessor, but broadly refers to a microcontroller,a microcomputer, a programmable logic controller, anapplication-specific integrated circuit, and any other programmablecircuit.

In one aspect, interfaces 15 are provided as network interface cards(NICs). Generally, NICs control the sending and receiving of datapackets over a computer network; other types of interfaces 15 may forexample support other peripherals used with computing device 10. Amongthe interfaces that may be provided are Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces,graphics interfaces, and the like. In addition, various types ofinterfaces may be provided such as, for example, universal serial bus(USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radiofrequency (RF), BLUETOOTH™, near-field communications (e.g., usingnear-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fastEthernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) orexternal SATA (ESATA) interfaces, high-definition multimedia interface(HDMI), digital visual interface (DVI), analog or digital audiointerfaces, asynchronous transfer mode (ATM) interfaces, high-speedserial interface (HSSI) interfaces, Point of Sale (POS) interfaces,fiber data distributed interfaces (FDDIs), and the like. Generally, suchinterfaces 15 may include physical ports appropriate for communicationwith appropriate media. In some cases, they may also include anindependent processor (such as a dedicated audio or video processor, asis common in the art for high-fidelity AN hardware interfaces) and, insome instances, volatile and/or non-volatile memory (e.g., RAM).

Although the system shown in FIG. 11 illustrates one specificarchitecture for a computing device 10 for implementing one or more ofthe aspects described herein, it is by no means the only devicearchitecture on which at least a portion of the features and techniquesdescribed herein may be implemented. For example, architectures havingone or any number of processors 13 may be used, and such processors 13may be present in a single device or distributed among any number ofdevices. In one aspect, a single processor 13 handles communications aswell as routing computations, while in other aspects a separatededicated communications processor may be provided. In various aspects,different types of features or functionalities may be implemented in asystem according to the aspect that includes a client device (such as atablet device or smartphone running client software) and server systems(such as a server system described in more detail below).

Regardless of network device configuration, the system of an aspect mayemploy one or more memories or memory modules (such as, for example,remote memory block 16 and local memory 11) configured to store data,program instructions for the general-purpose network operations, orother information relating to the functionality of the aspects describedherein (or any combinations of the above). Program instructions maycontrol execution of or comprise an operating system and/or one or moreapplications, for example. Memory 16 or memories 11, 16 may also beconfigured to store data structures, configuration data, encryptiondata, historical system operations information, or any other specific orgeneric non-program information described herein.

Because such information and program instructions may be employed toimplement one or more systems or methods described herein, at least somenetwork device aspects may include nontransitory machine-readablestorage media, which, for example, may be configured or designed tostore program instructions, state information, and the like forperforming various operations described herein. Examples of suchnontransitory machine-readable storage media include, but are notlimited to, magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks, and hardware devices that are speciallyconfigured to store and perform program instructions, such as read-onlymemory devices (ROM), flash memory (as is common in mobile devices andintegrated systems), solid state drives (SSD) and “hybrid SSD” storagedrives that may combine physical components of solid state and hard diskdrives in a single hardware device (as are becoming increasingly commonin the art with regard to personal computers), memristor memory, randomaccess memory (RAM), and the like. It should be appreciated that suchstorage means may be integral and non-removable (such as RAM hardwaremodules that may be soldered onto a motherboard or otherwise integratedinto an electronic device), or they may be removable such as swappableflash memory modules (such as “thumb drives” or other removable mediadesigned for rapidly exchanging physical storage devices),“hot-swappable” hard disk drives or solid state drives, removableoptical storage discs, or other such removable media, and that suchintegral and removable storage media may be utilized interchangeably.Examples of program instructions include both object code, such as maybe produced by a compiler, machine code, such as may be produced by anassembler or a linker, byte code, such as may be generated by forexample a JAVA™ compiler and may be executed using a Java virtualmachine or equivalent, or files containing higher level code that may beexecuted by the computer using an interpreter (for example, scriptswritten in Python, Perl, Ruby, Groovy, or any other scripting language).

In some aspects, systems may be implemented on a standalone computingsystem. Referring now to FIG. 12, there is shown a block diagramdepicting a typical exemplary architecture of one or more aspects orcomponents thereof on a standalone computing system. Computing device 20includes processors 21 that may run software that carry out one or morefunctions or applications of aspects, such as for example a clientapplication 24. Processors 21 may carry out computing instructions undercontrol of an operating system 22 such as, for example, a version ofMICROSOFT WINDOWS™ operating system, APPLE macOS™ or iOS™ operatingsystems, some variety of the Linux operating system, ANDROID™ operatingsystem, or the like. In many cases, one or more shared services 23 maybe operable in system 20, and may be useful for providing commonservices to client applications 24. Services 23 may for example beWINDOWS™ services, user-space common services in a Linux environment, orany other type of common service architecture used with operating system21. Input devices 28 may be of any type suitable for receiving userinput, including for example a keyboard, touchscreen, microphone (forexample, for voice input), mouse, touchpad, trackball, or anycombination thereof. Output devices 27 may be of any type suitable forproviding output to one or more users, whether remote or local to system20, and may include for example one or more screens for visual output,speakers, printers, or any combination thereof. Memory 25 may berandom-access memory having any structure and architecture known in theart, for use by processors 21, for example to run software. Storagedevices 26 may be any magnetic, optical, mechanical, memristor, orelectrical storage device for storage of data in digital form (such asthose described above, referring to FIG. 11). Examples of storagedevices 26 include flash memory, magnetic hard drive, CD-ROM, and/or thelike.

In some aspects, systems may be implemented on a distributed computingnetwork, such as one having any number of clients and/or servers.Referring now to FIG. 13, there is shown a block diagram depicting anexemplary architecture 30 for implementing at least a portion of asystem according to one aspect on a distributed computing network.According to the aspect, any number of clients 33 may be provided. Eachclient 33 may run software for implementing client-side portions of asystem; clients may comprise a system 20 such as that illustrated inFIG. 12. In addition, any number of servers 32 may be provided forhandling requests received from one or more clients 33. Clients 33 andservers 32 may communicate with one another via one or more electronicnetworks 31, which may be in various aspects any of the Internet, a widearea network, a mobile telephony network (such as CDMA or GSM cellularnetworks), a wireless network (such as WiFi, WiMAX, LTE, and so forth),or a local area network (or indeed any network topology known in theart; the aspect does not prefer any one network topology over anyother). Networks 31 may be implemented using any known networkprotocols, including for example wired and/or wireless protocols.

In addition, in some aspects, servers 32 may call external services 37when needed to obtain additional information, or to refer to additionaldata concerning a particular call. Communications with external services37 may take place, for example, via one or more networks 31. In variousaspects, external services 37 may comprise web-enabled services orfunctionality related to or installed on the hardware device itself. Forexample, in one aspect where client applications 24 are implemented on asmartphone or other electronic device, client applications 24 may obtaininformation stored in a server system 32 in the cloud or on an externalservice 37 deployed on one or more of a particular enterprise's oruser's premises. In addition to local storage on servers 32, remotestorage 38 may be accessible through the network(s) 31.

In some aspects, clients 33 or servers 32 (or both) may make use of oneor more specialized services or appliances that may be deployed locallyor remotely across one or more networks 31. For example, one or moredatabases 34 in either local or remote storage 38 may be used orreferred to by one or more aspects. It should be understood by onehaving ordinary skill in the art that databases in storage 34 may bearranged in a wide variety of architectures and using a wide variety ofdata access and manipulation means. For example, in various aspects oneor more databases in storage 34 may comprise a relational databasesystem using a structured query language (SQL), while others maycomprise an alternative data storage technology such as those referredto in the art as “NoSQL” (for example, HADOOP CASSANDRA™, GOOGLEBIGTABLE™, and so forth). In some aspects, variant databasearchitectures such as column-oriented databases, in-memory databases,clustered databases, distributed databases, or even flat file datarepositories may be used according to the aspect. It will be appreciatedby one having ordinary skill in the art that any combination of known orfuture database technologies may be used as appropriate, unless aspecific database technology or a specific arrangement of components isspecified for a particular aspect described herein. Moreover, it shouldbe appreciated that the term “database” as used herein may refer to aphysical database machine, a cluster of machines acting as a singledatabase system, or a logical database within an overall databasemanagement system. Unless a specific meaning is specified for a givenuse of the term “database”, it should be construed to mean any of thesesenses of the word, all of which are understood as a plain meaning ofthe term “database” by those having ordinary skill in the art.

Similarly, some aspects may make use of one or more security systems 36and configuration systems 35. Security and configuration management arecommon information technology (IT) and web functions, and some amount ofeach are generally associated with any IT or web systems. It should beunderstood by one having ordinary skill in the art that anyconfiguration or security subsystems known in the art now or in thefuture may be used in conjunction with aspects without limitation,unless a specific security 36 or configuration system 35 or approach isspecifically required by the description of any specific aspect.

FIG. 14 shows an exemplary overview of a computer system 40 as may beused in any of the various locations throughout the system. It isexemplary of any computer that may execute code to process data. Variousmodifications and changes may be made to computer system 40 withoutdeparting from the broader scope of the system and method disclosedherein. Central processor unit (CPU) 41 is connected to bus 42, to whichbus is also connected memory 43, nonvolatile memory 44, display 47,input/output (I/O) unit 48, and network interface card (NIC) 53. I/Ounit 48 may, typically, be connected to peripherals such as a keyboard49, pointing device 50, hard disk 52, real-time clock 51, a camera 57,and other peripheral devices. NIC 53 connects to network 54, which maybe the Internet or a local network, which local network may or may nothave connections to the Internet. The system may be connected to othercomputing devices through the network via a router 55, wireless localarea network 56, or any other network connection. Also shown as part ofsystem 40 is power supply unit 45 connected, in this example, to a mainalternating current (AC) supply 46. Not shown are batteries that couldbe present, and many other devices and modifications that are well knownbut are not applicable to the specific novel functions of the currentsystem and method disclosed herein. It should be appreciated that someor all components illustrated may be combined, such as in variousintegrated applications, for example Qualcomm or Samsungsystem-on-a-chip (SOC) devices, or whenever it may be appropriate tocombine multiple capabilities or functions into a single hardware device(for instance, in mobile devices such as smartphones, video gameconsoles, in-vehicle computer systems such as navigation or multimediasystems in automobiles, or other integrated hardware devices).

In various aspects, functionality for implementing systems or methods ofvarious aspects may be distributed among any number of client and/orserver components. For example, various software modules may beimplemented for performing various functions in connection with thesystem of any particular aspect, and such modules may be variouslyimplemented to run on server and/or client components.

The skilled person will be aware of a range of possible modifications ofthe various aspects described above. Accordingly, the present inventionis defined by the claims and their equivalents.

What is claimed is:
 1. A system for zero-step customer proximitydetection using mobile device low emissions beacons, comprising: adatabase comprising customer information, the customer informationcomprising: a list of registered wireless mobile devices; a deviceidentifier for each registered wireless mobile device; a photograph of acustomer associated with each registered wireless mobile device; ashort-range low-energy wireless network beacon comprising a firstmemory, a first processor, and a first plurality of programminginstructions stored in the first memory, and operating on the firstprocessor, wherein the first plurality of programming instructions, whenoperating on the processor, cause the payment facilitation device to:emit a beacon signal with short-range wireless communications; whereinthe beacon signal includes identifying information and applicationinformation from the short-range low-energy wireless network beacon;receive responses from mobile devices reached by the emitted beaconsignal; communicate with a database comprising customer information todetermine the identity of the responding mobile device owner; a mobiledevice comprising a second memory, a second processor, and a secondplurality of programming instructions stored in the second memory, andoperating on the second processor, wherein the second plurality ofprogramming instructions, when operating on the processor, cause thepayment facilitation device to: receive a signal emitted by ashort-range low-energy wireless network beacon; send the receivedinformation to a business server; respond to a beacon signal emitted bya short-range low-energy wireless network beacon; wherein the responseto a beacon signal emitted by a short-range low-energy wireless networkbeacon includes information on the relative distance between the twodevices based on the first received beacon signal; and a business servercomprising a third memory, a third processor, and a third plurality ofprogramming instructions stored in the third memory, and operating onthe third processor, wherein the third plurality of programminginstructions, when operating on the third processor, cause the businessserver to: receive identifying information from a mobile device;determine whether or not a matching photograph and other information ona user exists in a database comprising customer information exists forthe received identifying information; send the information from thedatabase comprising customer information that matches the receivedidentifying information, to the mobile device that sent the identifyinginformation; and enable communications with other connected mobiledevices to inform them of the identity and matching customer informationof the mobile device that interacted with the beacon.
 2. The system ofclaim 1, further comprising a zero-step authentication system, whereinthe zero-step authentication system is used to identify a customerwithout the need for a mobile device transmission, through the use ofbiometric identification.
 3. The system of claim 1, wherein theshort-range low-energy wireless network beacon is part of a mobiledevice operated by a business employee.
 4. The system of claim 1,wherein the short-range low-energy wireless network beacon is part of adesk-affixed device for servicing customers at the front-end of abusiness establishment.
 5. The system of claim 1, wherein theshort-range low-energy wireless network beacon is a device affixed to apart of a building, wherein the short-range low-energy wireless networkbeacon is capable of reaching customers that may walk by a businessestablishment.
 6. The system of claim 1, wherein the business serverfurther comprises a point-of-sale system, and wherein the databasecomprising customer information further includes information on pastcustomer interactions and customer preferences, and wherein theshort-range low-energy wireless network beacon further communicates withthe database comprising customer information to determine thepreferences or past sales information of an identified customer andprovides personalized communications with the mobile device based on thecustomer identity.
 7. A method for zero-step customer proximitydetection using mobile device low emissions beacons, comprising thesteps of: emitting a beacon signal with short-range wirelesscommunications, using a short-range low-energy wireless network beacon;wherein the beacon signal includes identifying information andapplication information from the short-range low-energy wireless networkbeacon, using a short-range low-energy wireless network beacon;receiving responses from mobile devices reached by the emitted beaconsignal, using a short-range low-energy wireless network beacon;communicating with a database comprising customer information todetermine the identity of the responding mobile device owner, using ashort-range low-energy wireless network beacon; receiving a signalemitted by a short-range low-energy wireless network beacon, using amobile device; sending the received information to a business server,using a mobile device; responding to a beacon signal emitted by ashort-range low-energy wireless network beacon, using a mobile device;wherein the response to a beacon signal emitted by a short-rangelow-energy wireless network beacon includes information on the relativedistance between the two devices based on the first received beaconsignal, using a mobile device; receiving identifying information from amobile device, using a business server; determining whether or not amatching photograph and other information on a user exists in a databasecomprising customer information exists for the received identifyinginformation, using a business server; sending the information from thedatabase comprising customer information that matches the receivedidentifying information, to the mobile device that sent the identifyinginformation, using a business server; and enabling communications withother connected mobile devices to inform them of the identity andmatching customer information of the mobile device that interacted withthe beacon, using a business server.
 8. The method of claim 7, furthercomprising a zero-step authentication system, wherein the zero-stepauthentication system is used to identify a customer without the needfor a mobile device transmission, through the use of biometricidentification.
 9. The method of claim 7, wherein the short-rangelow-energy wireless network beacon is part of a mobile device operatedby a business employee.
 10. The method of claim 7, wherein theshort-range low-energy wireless network beacon is part of a desk-affixeddevice for servicing customers at the front-end of a businessestablishment.
 11. The method of claim 7, wherein the short-rangelow-energy wireless network beacon is a device affixed to a part of abuilding, wherein the short-range low-energy wireless network beacon iscapable of reaching customers that may walk by a business establishment.12. The method of claim 7, wherein the business server further comprisesa point-of-sale system, and wherein the database comprising customerinformation further includes information on past customer interactionsand customer preferences, and wherein the short-range low-energywireless network beacon further communicates with the databasecomprising customer information to determine the preferences or pastsales information of an identified customer and provides personalizedcommunications with the mobile device based on the customer identity.